-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bumped Axios version to ">=0.25.0" #1190
Conversation
@vpulim can you look at this PR . |
@aniltallam please update with the latest from master |
I think this is covered by #1192 |
I have conflicts when using this package with the latest Hope the axios in |
I Hope too, the axios updated! |
But this pr seems not work, the code related to axios need to update too. |
I believe it's an axios problem. They fixed it in the axios package itself, and it is supposed to be released on v1.2.0. |
I can confirm axios D:\code\node\soap-example>node mail_ws_test.js
requestToken result: ......
D:\code\node\soap-example>npm i -S axios
added 3 packages, changed 7 packages, and audited 140 packages in 6s
11 packages are looking for funding
run `npm fund` for details
5 vulnerabilities (1 moderate, 1 high, 3 critical)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
D:\code\node\soap-example>node mail_ws_test.js
TypeError: Cannot read properties of undefined (reading 'create')
at new HttpClient (D:\code\node\soap-example\node_modules\soap\lib\http.js:40:59)
at Object.open_wsdl (D:\code\node\soap-example\node_modules\soap\lib\wsdl\index.js:1270:48)
at openWsdl (D:\code\node\soap-example\node_modules\soap\lib\soap.js:70:16)
at D:\code\node\soap-example\node_modules\soap\lib\soap.js:48:13
at _requestWSDL (D:\code\node\soap-example\node_modules\soap\lib\soap.js:76:9)
at createClient (D:\code\node\soap-example\node_modules\soap\lib\soap.js:94:5)
at D:\code\node\soap-example\node_modules\soap\lib\soap.js:104:9
at new Promise (<anonymous>)
at Object.createClientAsync (D:\code\node\soap-example\node_modules\soap\lib\soap.js:103:12)
at main (D:\code\node\soap-example\mail_ws_test.js:64:31)
D:\code\node\soap-example>npm i -S [email protected]
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/axios
npm WARN peer axios@">=0.21.1" from [email protected]
npm WARN node_modules/soap
npm WARN soap@"^0.45.0" from the root project
npm WARN 1 more (the root project)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer axios@">=0.21.1" from [email protected]
npm WARN node_modules/soap
npm WARN soap@"^0.45.0" from the root project
changed 1 package, and audited 140 packages in 2s
11 packages are looking for funding
run `npm fund` for details
5 vulnerabilities (1 moderate, 1 high, 3 critical)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
D:\code\node\soap-example>node mail_ws_test.js
requestToken result: ......
D:\code\node\soap-example> |
The 1.2.0 version of |
plz resolve the conflicts |
No it was a mistake. Didn't realize axios was 1.0. Should probably just upgrade this package? |
I wouldn't upgrade the peer dependency to |
It was just the latest available version at the time |
I am able to work with axios v1.x by using the
|
Can we mark the peer dependency to support old and new versions?
|
No need to be any more restrictive than what this PR already proposes:
|
Should not be problem anymore, new version released with updated axios. |
If the response size for any SOAP API is greater than 0x1fffffe8 characters then getting the following uncaught error and node process is crashing.
The issue is due to older version of Axios (https://github.com/axios/axios/blob/v0.21.1/lib/adapters/http.js#L253) not properly handling this error.
But this is fixed in v0.25.0 of Axios (https://github.com/axios/axios/blob/v0.25.0/lib/adapters/http.js#L302). So bumped the axios version to >=0.25.0 in the package.json